home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
rbbs_pc
/
rmail182.zip
/
EXAMPLE.CFG
< prev
next >
Wrap
Text File
|
1992-09-17
|
13KB
|
283 lines
; Example CONFIG file for RBBSMAIL RBBSMAIL 18.2
; All lines with a ';' in colum 1 are COMMENT lines, so are BLANK lines
;------------------------------------------------------------------------------
;first we need the addressing stuff.
;NOTICE: Beginnig RBBSMail v18.2 (wide beta), all addresses MUST be specified
;as full 4-dimensional ZONE:NET/NODE/POINT addresses.
;You may either specify a full ZONE:NET/NODE.POINT@DOMAIN or just the address
;with the domain name separately after the DOMAIN phrase.
ADDRESS 2:512/10.0@fidonet ;If the POINT part is not zero in the FIRST address
;listed, RBBSMail assumes you run as a POINT node.
ADDRESS 2:512/5.0@fidonet ;You may specify up to 10 extra (AKA) addresses
ADDRESS 2:2/508.0@fidonet ;AKA addresses are ignored for point setup
ADDRESS 8:998/0.0@rbbsnet
ADDRESS 8:998/1.0@rbbsnet
;------------------------------------------------------------------------------
;This phrase has become obsolete, you should specify full 5-dimensional
;addresses with the ADDRESS config phrase.
;DOMAIN fidonet
;------------------------------------------------------------------------------
; You may also have POINTS serviced by your system, so you have to tell
; RBBSMAIL what the number of the POINTNET is. There is one restriction,
; the number of your pointnet _MUST_ be the HIGHEST NUMBER in your list
; of nets!!
PRIVATENET 9999 ;Netnumber of private POINT network.
;------------------------------------------------------------------------------
;If you address points with their 2-dimensional fakenet address, it may be
;possible that your points send messages with their 4-dimennsional address.
;This causes the mail from the 4D points to be send back to their 2D address,
;which is not what we want. The Force2D configuration phrase tell RBBSMail
;to always treat any mail from a 4D point as if it were sent from a 2D
;fakenet address. note that this is ONLY for your own points, other points
;using 4D addresses will still be treated as 4D points.
Force2D
;------------------------------------------------------------------------------
;Where to find compressed mailbunldes
NETFILE C:\BT2\FILES
;------------------------------------------------------------------------------
;Where to put the outgoing mailbundles
HOLD C:\BT2\HOLD
;------------------------------------------------------------------------------
;This is to identify any ZONE or ECHO gates you send to or receive from,
;followed by the NET/NODE numbers that should ALWAYS appear in the SEEN-BY
;lines in messages adressed to that gate. Normally, the SEEN-BY line to an
;ECHOgate or ZONEgate will only contain the gate's NET/NODE and that of your
;own system (and, perhaps your own gateway AKA NET/NODE, if you have one).
;In case you are not the only system in your net calling the gate, the NET/NODE
;numbers of those other systems should also appear in the SEEN-BY line, UNLESS
;the gate also is your echo host (confused?)
;In all cases, the NET/NODE number should be in numeric order. Having a short
;SEEN-BY line keeps down the costs for ZONEand ECHO gates.
;It is assumed that mail, once send TO the gate will never get
;BACK from the gate to your system. You can have up to 25 gates defined. In
;the example, all messages to 2:2/1 will have "SEEN-BY: 1/2 512/10 101" as
;SEEN-BY line
;GATE is ignored for POINT setups.
;
GATE 1:1/2.0 1/2 512/10 999/999
GATE 2:2/1.0 2/1 512/10 999/999
GATE 2:28/0.0 28/0 512/1 10 999/99
GATE 3:3/2.0 3/2 512/10 999/999
;------------------------------------------------------------------------------
;Fake zone number of the DOMAIN you are the inbound Network Gateway for,
;followed by the origin line that replaces the origin line of incoming
;echomail from that network
INDOMAIN 8 RBBSNetwork Gateway to Europe (2:2/508.0)
;------------------------------------------------------------------------------
;RBBS-PC uses a SYSOP alias
SYSALIAS Buck Rogers
;------------------------------------------------------------------------------
;The SYSOP's real name
SYSOP John Sysop
;------------------------------------------------------------------------------
SIZE 9000 ;maximum size for TOSSing messages
;------------------------------------------------------------------------------
SECURITY 5 ;default security for imported messages
;------------------------------------------------------------------------------
; This tells RBBSMail what packer it should invoke. If you use the -OB or -OF
; commandline switches, an external packer like oMMM or mOOO should be
; configured here
; If you use RBBSMail's internal mailpacker by using either the -FA or -OF
; command switch, you need not configure the PACKER phrase. You then MAY
; configure the ARCmail options below
;
; NOTE: When calling a BATchfile here, you MUST explicitly call the BATchfile
; via a secondary copy of COMMAND.COM
pack oMMM -sa -j
;alternative PACK methods:
;PACK command.com /c RUN_OMMM.BAT
;pack ARCMAIL.EXE
;------------------------------------------------------------------------------
;RBBSMail can run the internal or external mailpacker (see above) after a
;certain number of messages have been exported. This keeps the individual
;mailbundles relatively small in size, which improves the performance if the
;destination node runs ConfMail or QM.
MAXOUT 100 ;# msg generated after which to shell to the packer
;------------------------------------------------------------------------------
;type of compression to use for individual destinations. A total of 100 nodes
;can be listed. Full ZONE:NET/NODE.POINT addresses must be listed.
;Repetitive address info on the same line may be omitted.
;
;The old trusted ARCA is the default. If a node is not listed here, he gets
;ARCmail, compressed by Vernon Buerg's ARCA.COM
;This is only applicable if you use RBBSMail's internal ARCmailer by giving
;either the -FA or the -OF option.
;
PAKto 2:512/10.1 .2 .3 ; these points get PAK format mailbundles
ARJto 2:555/666 ; this one gets ARJ packed mailbundles
LHAto 2:1010/2.0 ; he prefers LHA compressed mailbundles
ZIPto 8:900/2.0 3 4 5 ; but these guys can only handle ZIPped mailbundles
ZOOto 8:999/7.0 ; and finally a ZOO lover
;------------------------------------------------------------------------------
;Default ARcmail packing method is always Vernon Buerg's ARCA. If you want a
;different default, use the StdARCmail phrase
StdARCmail PKZIP ; or PAK, ARJ, LHA, ZOO
;------------------------------------------------------------------------------
;this line causes all redundant Ctrl-A kludges to be removed from all
;incoming echomail.
NoStinkingKludgeLines
;------------------------------------------------------------------------------
;set this option if you never want invalid echomail returned to the sender
NoRts
;------------------------------------------------------------------------------
; RBBSMail can send complaining messages to the originators of messages with
; certain defects. The warnings depend on the level setting of the NetBrick
; config phrase:
; 0 - disable sending of NetBricks
; 1 - Complain about Incorrect date/time fields (caused by braindead mailpackers)
; 2 - Complain about #1 and Missing Tearlines (caused by braindead sysops)
; 3 - Complain abour #1, #2 and if "SysOp" in the to/from field of messages was
; not changed to the SysOp's real name (caused by braindead echomail
; processors)
; 4 - Complain about #1, #2, #3 and redundant kludge lines (caused by Fidonet
; utility writers with a big ego). Level 4 also requires the phrase
; NoStinkingKludgeLines to be configured.
;
NetBrick 4
;------------------------------------------------------------------------------
;Some BinkleyTerm utilities (Yabom et al) expect a slightly different notation
;for ARCmail with a file-attach message. For some curious reason, Yabom needs a
;"#" in the attach message's subject field, right in front filename of the
;attached ARCmail bundle. By configuring the phrase below, RBBSMail will put
;the "3" where Yabom expects it to be.
;NOTE: Use this *ONLY* if you build ARCmail file-attaches (the -FA commandline
;switch) on a Binkley system. Please remember that the -OF commandline switch
;is the recommended way of building ARCmail on a Binkley system.
;YabomFA
;------------------------------------------------------------------------------
;set this option if you want Secure Mail always enabled
SecureMail
;------------------------------------------------------------------------------
;name of the logfile to use. If not specified, RBBSMAIL.LOG will be used.
;No log file runs slightly faster.
;StatusLog tosslog.log
;------------------------------------------------------------------------------
;level of detail for logfile, from 0 to 4.
LogLevel 4
;------------------------------------------------------------------------------
;Amount of msg IDs to retain when checking for messages. Can be 0....3200,
;default is 512. The larger the value, the more data has to be checked, which
;will slow down operation of RBBSMail.
;A value of 0 disables duplicate checking entirely.
DupSize 1024
;------------------------------------------------------------------------------
;If you want to conserve some space in your RBBS-PC conference files, set the
;StripSeen option. RBBSMail will then remove all SEEN-BY and PATH lines from
;messages imported to RBBS-PC style message bases.
StripSeen
;------------------------------------------------------------------------------
;This phrase tells RBBSMail to stamp local messages with the CURRENT date, not
;with the date the message was originally entered. If you kill messages by
;age, then the message age will be calculated from the moment the message
;arrived on your system
ImportDate
;------------------------------------------------------------------------------
;This phrase tells RBBSMail to store all local messages written to a FIDO style
;(*.MSG) message base in Opus/MAximus format. Extra date/time info is stored
;in the message header, which allows you to maintenance on the message bases
;using Opus or Maximus utilities like Renum or ReplyLink.
OpusDate
;------------------------------------------------------------------------------
;Kill messages without human readable contents
KillNull
;------------------------------------------------------------------------------
;Normally, RBBSMAil discards duplicate messages. However, you may wish to keep
;duplicate messages for manual inspection. With the KeepDups config phrase,
;you can tell RBBSMail to dump a copy of duplicate messages in the BAD_MSGS
;directory.
KeepDups
;------------------------------------------------------------------------------
;Dynamically purge message in case a RBBS-PC style message base fills up.
; +++++++++++++++++ READ THE DOCS BEFORE USE!! +++++++++++++++++++++++
DynaPurge
;------------------------------------------------------------------------------
;This configuration phrase is now obsolete. Please refer to RBBSMAIL.DOC for
;more details.
;ExportComments
;------------------------------------------------------------------------------
;If you do not have EMS mmeory and your are short on disk space, you may
; disable disk swapping
NoSwap
;------------------------------------------------------------------------------
;Where to swap RBBSMail to in case there is no or insufficient EMS/XMS
;memory free. If not configured, it defaults to the root of the current disk.
; +++++++++++++++++ READ THE DOCS BEFORE USE!! +++++++++++++++++++++++
SwapPath D:\TMP
;------------------------------------------------------------------------------
;For multi-tasking usage, you may wish to use NETBIOS file/record locking or
;the DESQview file locking methods
;For NETBIOS locking, include the full path\filename of your IBMFLAGS file.
;
;UseDV
;UseNETBIOS
;IBMFLAGS C:\RBBS\IBMFLAGS
;------------------------------------------------------------------------------
; RBBSMail will attempt to keep RBBS-PC style message bases at a fixed size.
; If you have set CONFIG to let the message file's size grow as messages are
; added, set the Elastic phrase to make optimum use of your disk space.
Elastic
; That's all!